Internet-Of Things Narrowband Communications with Mobile Satellite

ABSTRACT

A system and method for communicating with an Internet Of Things (IoT) device via a satellite link. The method includes assigning a transmission mode to a physical channel, where the physical channel supports multiple timeslot durations and the transmission mode is selected from a single user (SU) or a multi-user (MU); selecting a timeslot duration from the multiple durations for a payload; obtaining, when the transmission mode is SU, a timeslot grant for use of the physical channel for the timeslot duration; and transmitting a burst including the payload, where the burst is transmitted synchronized with the timeslot grant when the transmission mode is SU and the burst is transmitted without synchronization when the transmission mode is MU.

CROSS-REFERENCE TO RELATED APPLICATIONS AND INCORPORATION BY REFERENCE

The present application is a continuation of U.S. patent applicationSer. No. 17/325,289, filed May 20, 2021, and claims the benefit under 35U.S.C. 119(e) of U.S. Provisional Application Ser. No. 63/028,931, filedMay 22, 2020, which are all incorporated herein by reference in theirentireties.

FIELD

A system and method for narrowband Internet of Things (IoT) serviceswith a waveform, a baseband processing of a terminal transmitter and aRadio Access Network (RAN). The present teachings support sub-bandchannelization to enable easy migration of existing mobile satelliteinto next generation system with, for example, multiple tier IoTservices.

BACKGROUND

In a conventional communication system, rate matching or multiple codepoints or multiple burst types can be used to carry many differentmessage sizes. For an IoT application, however, the support of variablemessage size imposes complexity for terminal as well as gatewayimplementation. A small number of different sizes for the message oreven one size for the message is preferred for massive low cost IoTdevice development. Typical IoT message size being small, any overheadsuch as upper layer header and CRC portion significantly affect theoverall utilization efficiency of the burst. To make the situation morechallenging, although absolute size of the IoT message is smaller thanconventional data communication, the message size can vary depending ona type of IoT services.

There is also a need for satellite NB-IoT devices to use less power.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that is further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

A system of one or more computers can be configured to performparticular operations or actions by virtue of having software, firmware,hardware, or a combination of them installed on the system that inoperation causes or cause the system to perform the actions. One or morecomputer programs can be configured to perform particular operations oractions by virtue of including instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the actions. Onegeneral aspect includes a method for communicating with an Internet OfThings (IoT) device via a satellite link. The method includes assigninga transmission mode to a physical channel, where the physical channelsupports multiple timeslot durations and the transmission mode isselected from a single user (SU) or a multi-user (MU); selecting atimeslot duration from the multiple durations for a payload; obtaining,when the transmission mode is SU, a timeslot grant for use of thephysical channel for the timeslot duration; and transmitting a burstincluding the payload, where the burst is transmitted synchronized withthe timeslot grant when the transmission mode is SU and the burst istransmitted without synchronization when the transmission mode is MU.Other embodiments of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

Implementations may include one or more of the following features. Themethod where the transmitting uses an instantaneous effectiveisotropically radiated power (EIRP) that is less than −3.5 dBW forclosing a link on the physical channel with a receiver. The method wherethe physical channel supports multiple symbol rates and each of themultiple symbol rates has a low peak to average power ratio (PAPR). Themethod may include calculating an optimal payload size based onoptimizing a burst utilization; and segmenting the payload, prior to thetransmitting, based on the optimal payload size.

The method may include placing the IoT device in a connected mode, anidle mode, or a power saving mode, wherein a power consumption rate ofthe power saving mode is less than both a power consumption rate of theidle mode and a power consumption rate of the connected mode. Theconnected mode may include a transmitting duration consuming atransmitting power, a receiving duration consuming a receiving power anda dormant duration consuming a dormant power, where the dormant power isless than both the transmitting power and the receiving power.

The method may include receiving, with a multiuser receiver, the burstwhen the transmission mode is MU. The transmitting may include repeatinga burst, where the receiving performs selection combining on therepeated bursts when the transmission mode is MU, and the receivingperforms maximum-ratio combining (MRC) on the repeated bursts when thetransmission mode is SU. The method may include aggregating a pluralityof basebands to define the baseband of the physical channel. The methodmay include dividing a baseband of the physical channel into sub-bands,where the transmission mode of each of the sub-bands is setindependently. Implementations of the described techniques may includehardware, a method or process, or computer software on acomputer-accessible medium.

One general aspect includes a system to communicate with an Internet ofThings (IoT) device via a satellite link. The system may include aphysical channel that is assigned a transmission mode, where thephysical channel supports multiple timeslot durations and thetransmission mode is selected from a single user (SU) or a multi-user(MU); and a transmitter: to select a timeslot duration from the multipletimeslot durations for a payload, to obtain, when the transmission modeis SU, a timeslot grant for use of the physical channel for the timeslotduration, and to transmit a burst may include the payload, where theburst is transmitted synchronized with the timeslot grant when thetransmission mode is SU and the burst is transmitted withoutsynchronization when the transmission mode is MU. Other embodiments ofthis aspect include corresponding computer systems, apparatus, andcomputer programs recorded on one or more computer storage devices, eachconfigured to perform the actions of the methods.

Additional features will be set forth in the description that follows,and in part will be apparent from the description, or may be learned bypractice of what is described.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the way, the above-recited and other advantages andfeatures may be obtained, a more particular description is providedbelow and will be rendered by reference to specific embodiments thereofwhich are illustrated in the appended drawings. Understanding that thesedrawings depict only typical embodiments and are not, therefore, to belimiting of its scope, implementations will be described and explainedwith additional specificity and detail using the accompanying drawings.

FIG. 1A illustrates a ¼x physical channel according to variousembodiments.

FIG. 1B illustrates a 1x physical channel according to variousembodiments.

FIG. 1C illustrates a 5x physical channel according to variousembodiments.

FIG. 2 illustrates some key attributes of the ¼x, 1x and 5x forwardphysical channels according to various embodiments.

FIG. 3 illustrates some key attributes of the ¼x and 1x return physicalchannels according to various embodiments.

FIG. 4 illustrates transmission mode configurations for a physicalchannel, according to various embodiments.

FIG. 5 illustrates a multiuser receiver according to variousembodiments.

FIG. 6 illustrates an exemplary time and power diagram of a UT accordingto various embodiments.

FIG. 7 illustrates an exemplary enhanced power mode with an aggressiveduty cycling according to various embodiments.

FIG. 8 illustrates a message according to various embodiments.

FIG. 9 illustrates a method for determining an optimum payload size tominimize the overhead utilization while maximizing a burst utilizationfor payload delivery according to various embodiments.

FIG. 10A illustrates fractional overheads for various HO+CRC sizesaccording to various embodiments.

FIG. 10B illustrates fractional overheads for various filler sizesaccording to various embodiments.

FIG. 10C illustrates fractional overheads for various HO+CRC and fillersizes according to various embodiments.

FIG. 10D illustrates an overall fractional overhead according to variousembodiments.

FIG. 11 illustrates a method for communicating with an IoT device via asatellite link according to various embodiments.

Throughout the drawings and the detailed description, unless otherwisedescribed, the same drawing reference numerals will be understood torefer to the same elements, features, and structures. The relative sizeand depiction of these elements may be exaggerated for clarity,illustration, and convenience.

DETAILED DESCRIPTION

The present teachings may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as SMALLTALK, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general-purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Reference in the specification to “one embodiment” or “an embodiment” ofthe present invention, as well as other variations thereof, means that afeature, structure, characteristic, and so forth described in connectionwith the embodiment is included in at least one embodiment of thepresent invention. Thus, the appearances of the phrase “in oneembodiment” or “in an embodiment”, as well any other variations,appearing in various places throughout the specification are notnecessarily all referring to the same embodiment.

Introduction

Internet of Things (IoT) networks support massive number of lowthroughput devices. The present teachings leverage the Geo-Mobile Radio(GMR) standards laid out in GMR-1 3G/4G framework and advancedtechnology. The improvements allow for minimizing duty cycle/power atlow data rates while supporting massive connections. This enables lowcost IoT terminal development for use with satellites. A low cost andscalable Radio Access Network (RAN) is disclosed. With the presentteachings an existing satellite operator may enable low-costaugmentation of a satellite network to support IoT terminals thusproviding a cost efficient integrated terrestrial and satellite network.Value added service via an integrated Mobile Satellite Services (MSS)IoT solution. As such, traditional MSS services plus new satellite IoTservices may be offered.

The present teachings provide a flexible air interface numerology basedon GMR-1 with sub-band channelization for easy migration of existingmobile satellite into a next generation system with IoT services withmultiple tier IoT services. The present teaching support multiple set ofsymbol rates (bandwidth) and timeslot durations. A set of symbol rateand timeslot duration may be used for the traditional MSS services(non-IoT). Use of this set of symbol rate and timeslot duration may helpintroducing new terminals with traditional MSS services as well as IoT.

The multi-mode transmission provides reliable IoT transmission over asatellite link for a single user or multiple users. In some embodiments,multiple transmissions may be sent to improve reliability. Two differentmodes for may be supported: selection combining for multi-user (MU) modeand MRC combining for single user mode. The different modes minimize thegateway development cost and improve cost efficiency.

The present teachings are resource efficient and prevent spectrumfragmentation and maximize system spectrum utilization. In someembodiments, frequency-time resource sharing is provided to maximize thesystem throughput. Multiple sets of symbol rates (bandwidth) andtimeslot durations are supported. This includes the set of symbol rateand timeslot duration used for the traditional MSS services (non-IoT).By including the MSS set of symbol rate and timeslot duration resistanceto new terminals is reduced. In some embodiments, the present teachingsenable simultaneous transmission of multiple user message over the sametime and frequency resource.

Simple and effective coupled with ease of implementation provides for alow-cost terminal. Complexity may be moved to the gateway to provide anattractive solution for IoT devices having low-weight small-formfactordevices aimed for massive production. In some embodiments, a low-costterminal may support only one set with the smallest symbol rates.

The present teachings use ¼x, 1x or 5x symbol rate physical channels fora link, where x is a baseband. In GMR-1, 1x denotes a burst symbol rateof 23.4 ksps and a channel bandwidth of 31.25 kHz. Under thisconvention, 0.25x denotes dividing a 1x baseband physical channel into 4¼ sub-band physical channels having a burst symbol rate of 5.85 ksps anda channel bandwidth of 7.8125 kHz. 5x denotes aggregating five 1xbaseband physical channels into 1 5x physical channel having a burstsymbol rate of 117 ksps and a channel bandwidth of 156.25 kHz. In someembodiments, the aggregated baseband physical channels of the 5xphysical channel may include 5 contiguous basebands. In someembodiments, the aggregated baseband physical channels of the 5xphysical channel may include 5 non-contiguous basebands.

Forward Link

The present teachings use ¼x, 1x or 5x symbol rate bearer/physicalchannels for a forward link. IoT traffic may be conveyed with two typesof physical channels: Frequency Correction Channel and Packet NormalBursts. When a new symbol rate of ¼x may be used, the FCCH and PNB maybe prefixed with an “N”, i.e., NFCCH and NPNB. The forward link physicalchannel may support Discontinuation Reception (DRX) and a deep sleepmode to conserve a User Terminal battery life. The PNB may include aCyclic Redundancy Check (CRC) as an error-detecting code.

The FCCH is a chirp signal used for acquisition and synchronization. TheFCCH/NFCCH may be 80 ms long at ¼x (FIG. 1A, NFCCH 104, 114), 20 ms longat 1x (same as existing 20 ms FCCH3; FIG. 1B, FCCH 124, 134), and nottransmitted over 5x. Terminal may acquire FCCH on either 1x or 0.25x.FIG. 1C illustrates an FCCH 144, 154 that is 20 ms long and acquired viathe 1x signal.

The PNB/NPNB carries data and control messages. At ¼x, the PNB may be160 ms long and include 15 bytes (including a 2-byte CRC; FIG. 1A, NPNB106, 116). At 1x, the PNB may be 80 ms long and include 34 bytes(including a 2-byte CRC; FIG. 1B PNB 126, 136). At 5x, the PNB may be 20ms long and include 45 bytes (including 2-byte CRC; FIG. 1C, PNB 146,156). For a PNB, the Frame Error Rate (FER) of less than or equal to 1%at [−4] decibels in Additive White Gaussian Noise (AWGN).

The FCCHs and PNBs may be used to form a physical channel segmented intosuperframes. The superframes may be in 960 ms in length. In someembodiments, the first and optionally second PNB(s) of each superframemay be used to carry system information, an Uplink Map (ULMAP), aDownlink Map (DLMAP), in addition to user/control data.

FIG. 1A illustrates a ¼x physical channel according to variousembodiments. In FIG. 1A, a ¼x physical channel 100 includes superframes102, 112 of 960 ms each. A transmission of the superframes 102, 112 maybe a contiguous signal in the ¼x physical channel 100. In the physicalchannel 100, each of the superframes 102, 112 may include 2×80 ms NFCCHsand 5×160 ms NPNBs. 0.25x permits a whole system using 1x (31.25 kHz) BWusing a reuse factor of 4.

FIG. 1B illustrates a 1x physical channel according to variousembodiments.

In FIG. 1B, a 1x physical channel 120 includes superframes 122, 132 of960 ms each. A transmission of the superframes 122, 132 may be acontiguous signal in the physical channel 120. In the 1x physicalchannel 120, each of the superframes 122, 122 may include 4×20 ms FCCHsand 11×80 ms PNBs. 1x minimizes terminal receive on time compared to0.25x and may prolong battery life.

FIG. 1C illustrates a 5x physical channel according to variousembodiments. In FIG. 1C, a 5x physical channel 140 includes superframes142, 152 of 960 ms each. A transmission of the superframes 142, 152 maybe a contiguous signal in the 5x physical channel 140. In the 5xphysical channel 140, each of the superframes 142, 152 may include 48×20ms PNBs. FCCHs for use with a the 5x physical channel 140 may beacquired from a 1x physical channel interspersing 4×20 ms FCCHs in eachof the superframes 142, 152. 5x allows a transport of bigger size packetin a power efficient manner.

FIG. 2 illustrates some key attributes of the ¼x, 1x and 5x forwardphysical channels according to various embodiments.

A table 200 illustrates some key attributes of the ¼x, 1x and 5x forwardphysical channels. As seen in table 2, a PNB(1,48) may have two typesForward Error Correction (FEC): FEC with conventional encoding and FECwith Turbo encoding. NPNB(0.25,96) includes only conventional encodingto support low-cost terminals with less processing power. The 5xOperation assumes a UT acquiring a normal CCCH for system informationand initial synchronization.

Return Link

The present teachings disclose two types of physical channel that may beused for a link: ¼x based narrow band IoT physical channel and 1x basedIoT physical channel. The type of physical channel selected depends onavailable carrier bandwidth. The 0.25x physical channel enables highlyreliable link with IoT devices and minimizes required instantaneousEffective Isotropically Radiated Power (EIRP) as low as −5 dBW for alink closure. In some embodiments, the EIRP is less than −3 dBW, lessthan −3.5 dBW, less than −4 dBW or the like. The 1x physical channelwith a shorter timeslot duration minimizes overall service delay. Insome embodiments, a π/2-BPSK modulation with a low PAP_(R) provides forhigher amplifier efficiency, i.e., higher link margin. A return link mayenable one shot random access with a payload as big as 41 bytes; forNB-IoT this can minimize conventional two phased transmission (randomAccess followed by data session). The return link can enable multipleuser detection (MUD) at RAN to support massive connections. In someembodiments, a hybrid mode of multi and single user receptions may beprovided to allow a balance between efficient bandwidth utilization andlink performance.

An NPNB carries data and control messages in these physical channels.The present teachings provide for up to two burst lengths for each ofthe 0.25x and 1x physical channels. As a baseline, a 0.25x physicalchannel may transport 41 bytes including 2-byte CRCs in 960 ms, while a1x physical channel may need 240 ms to transport the same number ofbytes.

In some embodiments, shorter messages of only 10 bytes (1-byte CRC) maybe transported in 480 ms by a ¼x channel and in 120 ms by a 1x channel.Some burst types may be optimized for a packet size of less than orequal to 10 bytes, for example, initial access, resource request,ACK/NACK. High timing and frequency uncertainty burst types may beoptimized for a packet size of less than or equal to 10 bytes. In someembodiments, the transmissions may be synchronous with a frame startclock. In other embodiments, the transmissions may be synchronous with asymbol start clock.

The present teachings support Time Division Multiple Access (TDMA) withMultiple User Detection (MUD). In some embodiments, up to 4˜5simultaneous users per 0.25x physical channel may be supported assumingthat each of the simultaneous users transmit a 41-byte message over 0.96sec. With this assumption, the present teachings may transmit more than6000 messages/min over a 156.25 kHz band (i.e., over 8.6 millionmessages/day over 156.25 kHz). The present teachings support consecutivemultiple transmissions. One or more of the multiple transmissions may bea repetitive transmission.

FIG. 3 illustrates some key attributes of the ¼x and 1x return physicalchannels according to various embodiments.

A table 300 illustrates some key attributes of the ¼x and 1x returnphysical channels. As seen in table 300, a NPNB(0.25,288) and PNB(1,72)may have two types of FEC: FEC with convolutional encoding and FEC withTurbo encoding. The FEC with only conventional encoding supportslow-cost terminals with less processing power.

A Return guard period may be set around +/−12.5 ms for GEO environmentover a wide beam and may be used in conjunction with a synchronizationdesign. One-shot transmission may be supported using a 240 ms or 960 msburst to carry a message 41-bytes (including 2-byte CRC). The 41-bytemessage minimizes segmentation of a message and hence reduces transmiton time and receive on time for waiting acknowledgement. The 120 ms, 480ms burst may be used for a small packet size 10 bytes (such as initialaccess, resource request, ACK/NACK, or the like) and high timing andfrequency uncertainty.

FIG. 4 illustrates transmission mode configurations for a physicalchannel, according to various embodiments.

The present teachings support placing a physical channel in single user(SU) or multiple user (MU) transmission mode. A physical channel may bedynamically placed in SU or MU transmission modes. A hybrid transmissionmode intermittently changes the transmission mode between MU and SUmodes. For hybrid use bands (SU and MU in the same band), switchingbetween the two modes may be TDMA based. In FIG. 4 , band F4 is assignedSU mode for SU transmissions, band F1 is assigned MU mode for MUtransmissions, and bands F2 and F3 are for a hybrid usage where thetransmission mode is switch between SU and MU according to a time plan.As such, flexible hybrid and fixed mode configurations may be providedfor a frequency resource.

A SU UT may operate as contention-free device. Contention freetransmission may be provided by a grant frequency and/or timeslotprotocol, for example, the existing frequency and timeslot protocolproviding an uplink or downlink map on the forward channel. To operatewith the grant protocol, the SU UT may include a receiver in someembodiments. To avoid collisions over the SU channel, a SU UT requestsbandwidth allocation prior to transmitting.

In the single user mode, a FER≤0.1% at [−6] dB may be attained in AWGN.In the Multi-user mode, a FER≤1% at [−6] dB may be obtained in AWGN. InSU mode, a transmission repetition may be used to improve a link margin.For example, L transmissions of a message may lead to an increased SNRat the receiver: SNR→L×SNR. In contrast, in practical MU modeimplementations, L transmissions of a message do not lead to an L x SNRimprovement at the receiver. However, in the MU mode, L transmissions doimprove the probability of a successful reception, for example, from :P_(e)→P_(e) ^(L).

Multiuser Receiver RAN High Level Signal Processing

FIG. 5 illustrates a multiuser receiver according to variousembodiments.

FIG. 5 illustrates a satellite network 500 including UTs 502, asatellite 518 and a multiuser receiver 520. The UTs 502 may transmit aburst 560 on a physical channel 512—here UT1, UT2, UT3 and UT4 transmiton the physical channel 512. The bursts 560 may be received by thesatellite 518. The satellite 518 may forward a composite signal 516including all the bursts 560 (without any realignment) to the multiuserreceiver 520. A timeslot duration 556 of each the bursts 560 need not besame.

In MU transmission mode, more than one of the UTs 502 may betransmitting on the physical channel 512 at an instant. In MUtransmission mode, the UTs 502 may transmit bursts 560 asynchronously asillustrated by chart 550. In MU transmission mode, the UTs 502 maytransmit a burst 560 without regard to a frame boundary 558. In MUtransmission mode, a start instant 552 of the bursts 560 need not be thesame. In MU transmission mode, an end instant 554 of the bursts 560 neednot be the same.

In SU transmission mode, a timeslot grant may be obtained prior totransmission of the burst 560 by the UT 502. In SU transmission mode,the timeslot grant may be synchronized with the frame boundary 558. InSU transmission, bursts 560 from the UTs 502 do not overlap in time,ever partially (not shown).

The multiuser receiver 520 may be disposed at a gateway for receiveprocessing. In some embodiments, the multiuser receiver 520 may processthe signals per the physical channel 512. The multiuser receiver 520 mayinclude a channelizer 522, an acquisition and detection module 523, atracking module 524, an demodulators and interference cancellationmodule 526, and decoders 528.

The composite signal 516 may be provided to the channelizer 522 toselect a channel of interest from the composite signal 516. The channelor matched filter output of the channelizer 522 may be provided to theacquisition and detection module 523 to perform Unique Word (UW) basedcorrelation and detection. In some embodiments, when iterativeacquisition is used, outputs 529 of decoders 528 may be used theacquisition and detection module 523. The acquisition and detectionmodule 523 outputs a count of detected users, coarse timing, frequency,and a Signal to Noise Ratio (SNR) for each user.

The channel or matched filter output from the channelizer 522 and theoutput of the acquisition and detection module 523 may be provided tothe tracking module 524 to perform finer timing, frequency estimation,phase estimation and SNR for each user. In some embodiments, outputs 529of all the decoders 528 may be provided to the tracking module 524. Thetracking module 524 may output refined timing, frequency, phase, SNR,sync error compensated I&Q stream for each user.

The channel or matched filter output from the channelizer 522 and theoutput of the tracking module 524 may be provided to the demodulatorsand interference cancellation module 526 to provide interferencecancellation and soft output generation for each use. In someembodiments, outputs 529 of all the decoders 528 may be provided to thedemodulators and interference cancellation module 526. The output of thedemodulators and interference cancellation module 526 is a soft input tothe decoders 528.

The soft output from the interference cancellation module 526 may beprovided to the decoders 528. The outputs 529 of the decoders 528 aredecoded bursts including the burst payload. There may an independentdecoder for each user and extrinsic information generation for eachuser. In some embodiments, a user specific scrambling/interleavingmodule (not shown) may be disposed between interference cancellationmodule 526 and the decoders 528. The decoders may be Single-InSingle-Out (SISO) or the like decoders.

Each UT 502 may include a UT transmitter 530. The UT transmitter 530 mayinclude a CRC encoding module 532, an FEC encoding module 534, arepetition coding module 536, an interleaving/scrambling module 538, amodulator module 540, a burst formatting module 542 and a pulse shapingmodule 544. The UT transmitter 530 may receive a payload as an input andgenerate an output to be processed by a Digital to Analog Converter(DAC) prior to transmission. Each UT 502 may include a power module (notshown) to place the UT 502 in a connected mode, an idle mode, or a powersaving mode.

A multi-user receiver differs from a conventional TDMA receiver as thereceiver must detect, demodulate, and decode bursts received frommultiple users sharing a same time and frequency resource. The receivermay be configured is contention based or contention free. in aContention based configuration, the receiver operates similar to anexisting RACH receiver except for MU detections. In contention-basedconfiguration, the UT may operate as a Grant free Terminal, where thetransmission is based on a timer, a backlog, ability of the receiver todetect multiple transmissions and separate them. The Contention freeconfiguration may be the same as an existing uplink grant based packetdata channel. The configuration can be selected per a physicalchannel/timeslot basis as illustrated in FIG. 4 .

The receiver may be robust enough to provide a required Quality ofService (QoS). For example, the receiver may be configured for adedicated user. However, there may be an unintended signal collision dueto other user transmission. Such an event may be due to an error in thedownlink reception or other practical scheduling related errorscenarios.

Terminal Power Saving

In the prior art, for example, the GMR-1 3G standard, a UT may be in anidle mode or a connected mode. Furthermore, a Dormant Power (P_(D)) forthe UT is less than a Transmit Power (P_(T)) or a Receive Power (P_(R))consumed by the UT for an interval. In idle mode, the UT consumes P_(R),P_(T) and P_(D) in various intervals. In the connected mode of the priorart, the UT consumes P_(R) and P_(T) in various intervals; when nottransmitting the UT defaults to P_(R) (not P_(D)).

FIG. 6 illustrates an exemplary time and power diagram of a UT accordingto various embodiments.

The present teachings disclose a power plan 600 including a power savingmode 602, an idle mode 604 and a connected mode 606. The power plan 600may be implemented by a power module in a UT. In the power saving mode602, the UT consumes a Deep Sleep Power (P_(S)) 608. P_(S) 608 is lessthan a P_(D) 616. In some embodiments, a direct transition from aconnected mode 606 to the power saving mode 602 without going through anidle mode 604 is provided.

In some embodiments, the idle mode 604 remains unchanged from the priorart. In some embodiments, the connected mode 606 is enabled for aninterval. In the connected mode, a UT consumes P_(T) 612 for atransmitting duration T_(TX), P_(R) 614 for a receiving duration T_(RX),and P_(D) 616 for a dormant duration T_(D,C). The use of P_(D) 616 ismade feasible with a DLMAP and/or a ULMAP. With a DL-MAP, the UT candetermine what timeslot is assigned to it to receive information from agateway. Thus, the UT can save power by selectivelydemodulating/decoding only the assigned timeslots. As such, a UT needonly consume P_(D) 616 during unassigned timeslots in the connected mode606. In contrast, the prior art consumes P_(R) 634 during the unassignedtimeslots; P_(S) 608 is less than a P_(D) 616. In some embodiments, afirst and/or a second PNB may carry a DLMAP, a ULMAP, or systeminformation in addition to user/control data or an uplinkacknowledgement.

FIG. 7 illustrates an exemplary enhanced power mode with an aggressiveduty cycling according to various embodiments.

Assuming that a UT is configured to receive every hour (3600 seconds)with a 10 second window to receive data. As such, the UT wakes us every3590 seconds for a 10 second window in 3600 second intervals. Table 700compares power consumption by a UT utilizing deep sleep with a UTwithout deep sleep. For total usage in a day, significant energy saving(greater than 48x) by using smart power utilization including deep sleeppower consumption for 3590 seconds every 3600 seconds are obtained. Forexample, battery life of a UT powered with two AA batteries (5 Wh) maybe increased to 1.1 years when deep sleep is utilized rather than only8.2 days for a UT without deep sleep.

Sat NB-IoT Payload Optimization

FIG. 8 illustrates a signal according to various embodiments.

A signal 800 may include a burst 810 that conveys a MSG portion 802 of Xbytes. The burst 810 may include a HO portion 804 (header overhead) anda CRC portion 806 having a size of Y bytes (together referred asHO+CRC). The payload of the burst 810 is X+Y bytes. When a message sizeof the message is larger than X, the message may be transmitted overmultiple bursts 810, 810′. When mod(message size,X) is non-zero, theremainder mod(message size,X) bytes of the message may be transmitted inthe burst 810′ including mod(message size,X) bytes 802′ and filler bytes808. The burst 810′ may be used when a message size is smaller than X ormod (MSG,X) is non-zero. The burst 810 may be used when the message sizeis greater than or equal to X.

The MSG size (bytes) can be modeled as a random variable. The 3GPP IoTTraffic Model (MAR periodic reports) Truncated Pareto Distributionprovides that IoT traffic generally has the following characteristics:

-   -   Min: 20 bytes    -   Max: 200 bytes    -   Average=33 bytes    -   Standard Deviation=21 bytes    -   90 percentiles=50 bytes

FIG. 9 illustrates a method for determining an optimum payload size tominimize the overhead utilization while maximizing a burst utilizationfor payload delivery according to various embodiments.

FIG. 10A illustrates fractional overheads for various HO+CRC sizesaccording to various embodiments.

FIG. 10B illustrates fractional overheads for various filler sizesaccording to various embodiments.

FIG. 10C illustrates fractional overheads for various HO+CRC and fillersizes according to various embodiments.

FIG. 10D illustrates an overall fractional overhead according to variousembodiments.

FIG. 9 illustrates a method 900 to determine an optimum payload size tominimize the overhead utilization while maximizing a burst utilizationfor payload delivery. The method 900 includes an operation 902 that, forN HO+CRC sizes, computes a fractional overhead for each HO+CRC size (forexample, as illustrated in FIG. 10A). The method 900 includes anoperation 904 that, for N HO+CRC sizes, computes a fractional overheadfor each filler size (for example, as illustrated in FIG. 10B). Themethod 900 includes an operation 906 that, for N HO+CRC and fillersizes, computes overall fractional overheads for each (for example, asillustrated in FIG. 10C). The N overall fractional overheads foroperation 906 may be computed by, for example, adding the N fractionaloverheads of operation 902 with N fractional overheads of operation 904.The method 900 includes an operation 908 that computes an overallfractional overhead by averaging the N overall fractional overheads ofoperation 908 (for example, as illustrated in FIG. 10D). The method 900includes an operation 910 that finds the overall fractional minima todetermine an optimal payload size for an expected traffic. The overallfractional minima are illustrated as ellipse 1002 in FIG. 10D.

FIG. 11 illustrates a method for communicating with an IoT device via asatellite link according to various embodiments.

A method 1100 for communicating with an IoT device via a satellite linkmay include an operation 1102 to assign a transmission mode to aphysical channel, wherein the physical channel supports bursts ofmultiple timeslot durations and the transmission mode is selected fromSU or MU. The method 1100 may include operation 1104 to calculate anoptimal payload size based on optimizing a burst utilization. The method1100 may include operation 1106 to select a timeslot duration from themultiple timeslot durations for a payload The method 1100 may includeoperation 1108 to segment the payload, prior to the transmitting, basedon the optimal payload size. The method 1100 may include operation 1110to obtain, when the transmission mode is SU, a timeslot grant for use ofthe physical channel for the timeslot duration. The method 1100 mayinclude operation 1112 to transmit a burst including the payload,wherein the burst is transmitted synchronized with the timeslot grantwhen the transmission mode is SU and the burst is transmitted withoutsynchronization when the transmission mode is MU. The method 1100 mayinclude operation 1114 to receive the burst. The method 1100 may includeoperation 1116 to place the IoT device in a connected mode, an idlemode, or a power saving mode, wherein a power consumption rate of thepower saving mode is less than both a power consumption rate of the idlemode and a power consumption rate of the connected mode.

Having described preferred embodiments of a system and method (which areintended to be illustrative and not limiting), it is noted thatmodifications and variations can be made by persons skilled in the artconsidering the above teachings. It is therefore to be understood thatchanges may be made in the embodiments disclosed which are within thescope of the invention as outlined by the appended claims. Having thusdescribed aspects of the invention, with the details and particularityrequired by the patent laws, what is claimed and desired protected byLetters Patent is set forth in the appended claims.

We claim as our invention:
 1. A method for communicating with anInternet of Things (IoT) device via a satellite link, the methodcomprising: placing the IoT device in a connected mode, an idle mode, ora power saving mode, wherein a power consumption rate of the powersaving mode is less than both a power consumption rate of the idle modeand a power consumption rate of the connected mode, wherein theconnected mode comprises a transmitting duration consuming atransmitting power, a receiving duration consuming a receiving power anda dormant duration consuming a dormant power, wherein the dormant poweris less than both the transmitting power and the receiving power.
 2. Themethod of claim 1, further comprising transitioning directly from theconnected mode to the power saving mode.
 3. The method of claim 1,further comprising determining a transmitting duration based on ULMAP(Uplink MAP).
 4. The method of claim 1, further comprising determining areceiving duration based on a DLMAP (Downlink MAP).
 5. The method ofclaim 1, further comprising transmitting a burst comprising a payloadsynchronized with the transmitting duration.
 6. The method of claim 5,further comprising calculating an optimal payload size based onoptimizing a burst utilization; and segmenting the payload, prior to thetransmitting, based on the optimal payload size.
 7. The method of claim1, further comprising demodulating/decoding during the receivingduration of the connected mode.
 8. The method of claim 1, furthercomprising disabling a demodulating/decoding during the dormant durationof the connected mode.
 9. The method of claim 1, further comprisingreceiving, during the receiving duration, a burst.
 10. The method ofclaim 1, wherein the placing places the IoT device in a deep sleep modehaving a power consumption rate less than the power consumption rate ofthe power saving mode.
 11. A system to communicate with an Internet ofThings (IoT) device via a satellite link, the system comprising: a powermodule to place the IoT device in a connected mode, an idle mode, or apower saving mode, wherein a power consumption rate of the power savingmode is less than both a power consumption rate of the idle mode and apower consumption rate of the connected mode, wherein the connected modecomprises a transmitting duration consuming a transmitting power, areceiving duration consuming a receiving power and a dormant durationconsuming a dormant power, wherein the dormant power is less than boththe transmitting power and the receiving power.
 12. The system of claim11, wherein the power module transitions directly from the connectedmode to the power saving mode.
 13. The system of claim 11, wherein theIoT device determines a transmitting duration based on ULMAP (UplinkMAP).
 14. The system of claim 11, wherein the IoT device determines areceiving duration based on a DLMAP (Downlink MAP).
 15. The system ofclaim 11, further comprising a transmitter to transmit a burstcomprising a payload synchronized with the transmitting duration. 16.The system of claim 15, wherein the IoT device calculates an optimalpayload size based on optimizing a burst utilization; and segmenting thepayload, prior to the transmitting, based on the optimal payload size.17. The system of claim 11, further comprising a demodulator/decoder todemodulate/decode during the receiving duration of the connected mode.18. The system of claim 11, further comprising a demodulator/decoder tonot demodulate/decode during the dormant duration of the connected mode.19. The system of claim 11, further comprising a receiver to receive,during the receiving duration, a burst.
 20. The system of claim 11,wherein the power module places the IoT device in a deep sleep modehaving a power consumption rate less than the power consumption rate ofthe power saving mode.